Type theory

Short description: Concept in mathematical logic

In mathematics and theoretical computer science, a type theory is the formal presentation of a specific type system. Type theory is the academic study of type systems.

Some type theories serve as alternatives to set theory as a foundation of mathematics. Two influential type theories that have been proposed as foundations are Alonzo Church's typed λ-calculus and Per Martin-Löf's intuitionistic type theory.

Most computerized proof-writing systems use a type theory for their foundation. A common one is Thierry Coquand's Calculus of Inductive Constructions.

History

Type theory was created to avoid a paradox in a mathematical equation based on naive set theory and formal logic. Russell's paradox (first described in Gottlob Frege's The Foundations of Arithmetic) is that, without proper axioms, it is possible to define the set of all sets that are not members of themselves; this set both contains itself and does not contain itself. Between 1902 and 1908, Bertrand Russell proposed various solutions to this problem.

By 1908, Russell arrived at a ramified theory of types together with an axiom of reducibility, both of which appeared in Whitehead and Russell's Principia Mathematica published in 1910, 1912, and 1913. This system avoided contradictions suggested in Russell's paradox by creating a hierarchy of types and then assigning each concrete mathematical entity to a specific type. Entities of a given type were built exclusively of subtypes of that type, thus preventing an entity from being defined using itself. This resolution of Russell's paradox is similar to approaches taken in other formal systems, such as Zermelo-Faenkel set theory.

Type theory is particularly popular in conjunction with Alonzo Church's lambda calculus. One notable early example of type theory is Church's simply typed lambda calculus. Church's theory of types helped the formal system avoid the Kleene–Rosser paradox that afflicted the original untyped lambda calculus. Church demonstrated that it could serve as a foundation of mathematics and it was referred to as a higher-order logic.

In the modern literature, "type theory" refers to a typed system based around lambda calculus. One influential system is Per Martin-Löf's intuitionistic type theory, which was proposed as a foundation for constructive mathematics. Another is Thierry Coquand's calculus of constructions, which is used as the foundation by Coq, Lean, and other computer proof assistants. Type theory is an active area of research, one direction being the development of homotopy type theory.

Applications

Mathematical foundations

The first computer proof assistant, called Automath, used type theory to encode mathematics on a computer. Martin-Löf specifically developed intuitionistic type theory to encode all mathematics to serve as a new foundation for mathematics. There is ongoing research into mathematical foundations using homotopy type theory.

Mathematicians working in category theory already had difficulty working with the widely accepted foundation of Zermelo–Fraenkel set theory. This led to proposals such as Lawvere's Elementary Theory of the Category of Sets (ETCS). Homotopy type theory continues in this line using type theory. Researchers are exploring connections between dependent types (especially the identity type) and algebraic topology (specifically homotopy).

Proof assistants

Much of the current research into type theory is driven by proof checkers, interactive proof assistants, and automated theorem provers. Most of these systems use a type theory as the mathematical foundation for encoding proofs, which is not surprising, given the close connection between type theory and programming languages:

• LF is used by Twelf, often to define other type theories;
• many type theories which fall under higher-order logic are used by the HOL family of provers and PVS;
• computational type theory is used by NuPRL;
• calculus of constructions and its derivatives are used by Coq, Matita, and Lean;
• UTT (Luo's Unified Theory of dependent Types) is used by Agda which is both a programming language and proof assistant

Many type theories are supported by LEGO and Isabelle. Isabelle also supports foundations besides type theories, such as ZFC. Mizar is an example of a proof system that only supports set theory.

Programming languages

Any static program analysis, such as the type checking algorithms in the semantic analysis phase of compiler, has a connection to type theory. A prime example is Agda, a programming language which uses UTT (Luo's Unified Theory of dependent Types) for its type system.

The programming language ML was developed for manipulating type theories (see LCF) and its own type system was heavily influenced by them.

Linguistics

Type theory is also widely used in formal theories of semantics of natural languages, especially Montague grammar and its descendants. In particular, categorial grammars and pregroup grammars extensively use type constructors to define the types (noun, verb, etc.) of words.

The most common construction takes the basic types [math]\displaystyle{ e }[/math] and [math]\displaystyle{ t }[/math] for individuals and truth-values, respectively, and defines the set of types recursively as follows:

• if [math]\displaystyle{ a }[/math] and [math]\displaystyle{ b }[/math] are types, then so is [math]\displaystyle{ \langle a,b\rangle }[/math];
• nothing except the basic types, and what can be constructed from them by means of the previous clause are types.

A complex type [math]\displaystyle{ \langle a,b\rangle }[/math] is the type of functions from entities of type [math]\displaystyle{ a }[/math] to entities of type [math]\displaystyle{ b }[/math]. Thus one has types like [math]\displaystyle{ \langle e,t\rangle }[/math] which are interpreted as elements of the set of functions from entities to truth-values, i.e. indicator functions of sets of entities. An expression of type [math]\displaystyle{ \langle\langle e,t\rangle,t\rangle }[/math] is a function from sets of entities to truth-values, i.e. a (indicator function of a) set of sets. This latter type is standardly taken to be the type of natural language quantifiers, like everybody or nobody (Montague 1973, Barwise and Cooper 1981).

Type theory with records is a formal semantics representation framework, using records to express type theory types. It has been used in natural language processing, principally computational semantics and dialogue systems.

Social sciences

Gregory Bateson introduced a theory of logical types into the social sciences; his notions of double bind and logical levels are based on Russell's theory of types.

Type theory as a logic

A type theory is a mathematical logic, which is to say it is a collection of rules of inference that result in judgments. Most logics have judgments asserting "The proposition [math]\displaystyle{ \varphi }[/math] is true", or "The formula [math]\displaystyle{ \varphi }[/math] is a well-formed formula". A type theory has judgments that define types and assign them to a collection of formal objects, known as terms. A term and its type are often written together as [math]\displaystyle{ \mathrm{term}:\mathsf{type} }[/math].

Terms

A term in logic is recursively defined as a constant symbol, variable, or a function application, where a term is applied to another term. Constant symbols could include the natural number [math]\displaystyle{ 0 }[/math], the Boolean value [math]\displaystyle{ \mathrm{true} }[/math], and functions such as the successor function [math]\displaystyle{ \mathrm{S} }[/math] and conditional operator [math]\displaystyle{ \mathrm{if} }[/math]. Thus some terms could be [math]\displaystyle{ 0 }[/math], [math]\displaystyle{ (\mathrm{S}\,0) }[/math], [math]\displaystyle{ (\mathrm{S}\,(\mathrm{S}\,0)) }[/math], and [math]\displaystyle{ (\mathrm{if}\,\mathrm{true}\,0\,(\mathrm{S}\,0)) }[/math].

Judgments

Most type theories have 4 judgments:

• "[math]\displaystyle{ T }[/math] is a type"
• "[math]\displaystyle{ t }[/math] is a term of type [math]\displaystyle{ T }[/math]"
• "Type [math]\displaystyle{ T_1 }[/math] is equal to type [math]\displaystyle{ T_2 }[/math]"
• "Terms [math]\displaystyle{ t_1 }[/math] and [math]\displaystyle{ t_2 }[/math] both of type [math]\displaystyle{ T }[/math] are equal"

Judgments may follow from assumptions. For example, one might say "assuming [math]\displaystyle{ x }[/math] is a term of type [math]\displaystyle{ \mathsf{bool} }[/math] and [math]\displaystyle{ y }[/math] is a term of type [math]\displaystyle{ \mathsf{nat} }[/math], it follows that [math]\displaystyle{ (\mathrm{if}\,x\,y\,y) }[/math] is a term of type [math]\displaystyle{ \mathsf{nat} }[/math]". Such judgments are formally written with the turnstile symbol [math]\displaystyle{ \vdash }[/math].

[math]\displaystyle{ x:\mathsf{bool},y:\mathsf{nat}\vdash(\textrm{if}\,x\,y\,y): \mathsf{nat} }[/math]

If there are no assumptions, there will be nothing to the left of the turnstile.

[math]\displaystyle{ \vdash \mathrm{S}:\mathsf{nat}\to\mathsf{nat} }[/math]

The list of assumptions on the left is the context of the judgment. Capital greek letters, such as [math]\displaystyle{ \Gamma }[/math] and [math]\displaystyle{ \Delta }[/math], are common choices to represent some or all of the assumptions. The 4 different judgments are thus usually written as follows.

Formal notation for judgments	Description
[math]\displaystyle{ \Gamma \vdash T }[/math] Type	[math]\displaystyle{ T }[/math] is a type (under assumptions [math]\displaystyle{ \Gamma }[/math]).
[math]\displaystyle{ \Gamma \vdash t : T }[/math]	[math]\displaystyle{ t }[/math] is a term of type [math]\displaystyle{ T }[/math] (under assumptions [math]\displaystyle{ \Gamma }[/math]).
[math]\displaystyle{ \Gamma \vdash T_1 = T_2 }[/math]	Type [math]\displaystyle{ T_1 }[/math] is equal to type [math]\displaystyle{ T_2 }[/math] (under assumptions [math]\displaystyle{ \Gamma }[/math]).
[math]\displaystyle{ \Gamma \vdash t_1 = t_2 : T }[/math]	Terms [math]\displaystyle{ t_1 }[/math] and [math]\displaystyle{ t_2 }[/math] are both of type [math]\displaystyle{ T }[/math] and are equal (under assumptions [math]\displaystyle{ \Gamma }[/math]).

Some textbooks use a triple equal sign [math]\displaystyle{ \equiv }[/math] to stress that this is judgmental equality and thus an extrinsic notion of equality. The judgments enforce that every term has a type. The type will restrict which rules can be applied to a term.

Rules of Inference

A type theory's inference rules say what judgments can be made, based on the existence of other judgments. Rules are expressed as a Gentzen-style deduction using a horizontal line, with the required input judgments above the line and the resulting judgment below the line. For example, the following inference rule states a substitution rule for judgmental equality.[math]\displaystyle{ \begin{array}{c} \Gamma\vdash t:T_1 \qquad \Delta\vdash T_1 = T_2 \\ \hline \Gamma,\Delta\vdash t:T_2 \end{array} }[/math]The rules are syntactic and work by rewriting. The metavariables [math]\displaystyle{ \Gamma }[/math], [math]\displaystyle{ \Delta }[/math], [math]\displaystyle{ t }[/math], [math]\displaystyle{ T_1 }[/math], and [math]\displaystyle{ T_2 }[/math] may actually consist of complex terms and types that contain many function applications, not just single symbols.

To generate a particular judgment in type theory, there must be a rule to generate it, as well as rules to generate all of that rule's required inputs, and so on. The applied rules form a proof tree, where the top-most rules need no assumptions. One example of a rule that does not require any inputs is one that states the type of a constant term. For example, to assert that there is a term [math]\displaystyle{ 0 }[/math] of type [math]\displaystyle{ \mathsf{nat} }[/math], one would write the following.[math]\displaystyle{ \begin{array}{c} \hline \vdash 0 : nat \\ \end{array} }[/math]

Type inhabitation

Generally, the desired conclusion of a proof in type theory is one of type inhabitation. The decision problem of type inhabitation (abbreviated by [math]\displaystyle{ \exists t.\Gamma \vdash t : \tau? }[/math]) is:

Given a context [math]\displaystyle{ \Gamma }[/math] and a type [math]\displaystyle{ \tau }[/math], decide whether there exists a term [math]\displaystyle{ t }[/math] that can be assigned the type [math]\displaystyle{ \tau }[/math] in the type environment [math]\displaystyle{ \Gamma }[/math].

Girard's paradox shows that type inhabitation is strongly related to the consistency of a type system with Curry–Howard correspondence. To be sound, such a system must have uninhabited types.

A type theory usually has several rules, including ones to:

• create a judgment (known as a context in this case)
• add an assumption to the context (context weakening)
• rearrange the assumptions
• use an assumption to create a variable
• define reflexivity, symmetry and transitivity for judgmental equality
• define substitution for application of lambda terms
• list all the interactions of equality, such as substitution
• define a heirarchy of type universes
• assert the existence of new types

Also, for each "by rule" type, there are 4 different kinds of rules

• "type formation" rules say how to create the type
• "term introduction" rules define the canonical terms and constructor functions, like "pair" and "S".
• "term elimination" rules define the other functions like "first", "second", and "R".
• "computation" rules specify how computation is performed with the type-specific functions.

For examples of rules, an interested reader may follow Appendix A.2 of the Homotopy Type Theory book, or read Martin-Löf's Intuitionistic Type Theory.

Connections to foundations

The logical framework of a type theory bears a resemblance to intuitionistic, or constructive, logic. Formally, type theory is often cited as an implementation of the Brouwer–Heyting–Kolmogorov interpretation of intuitionistic logic. Additionally, connections can be made to category theory and computer programs.

Intuitionistic logic

When used as a foundation, certain types are interpreted to be propositions (statements that can be proven), and terms inhabiting the type are interpreted to be proofs of that proposition. When some types are interpreted as propositions, there is a set of common types that can be used to connect them to make a Boolean algebra out of types. However, the logic is not classical logic but intuitionistic logic, which is to say it does not have the law of excluded middle nor double negation.

Under this intuitionistic interpretation, there are common types that act as the logical operators:

Logic Name	Logic Notation	Type Notation	Type Name
True	[math]\displaystyle{ \top }[/math]	[math]\displaystyle{ \top }[/math]	Unit Type
False	[math]\displaystyle{ \bot }[/math]	[math]\displaystyle{ \bot }[/math]	Empty Type
Implication	[math]\displaystyle{ A \to B }[/math]	[math]\displaystyle{ A \to B }[/math]	Function
Not	[math]\displaystyle{ \neg A }[/math]	[math]\displaystyle{ A \to \bot }[/math]	Function to Empty Type
And	[math]\displaystyle{ A \land B }[/math]	[math]\displaystyle{ A \times B }[/math]	Product Type
Or	[math]\displaystyle{ A \lor B }[/math]	[math]\displaystyle{ A + B }[/math]	Sum Type
For All	[math]\displaystyle{ \forall a \in A, P(a) }[/math]	[math]\displaystyle{ \Pi a:A.P(a) }[/math]	Dependent Product
Exists	[math]\displaystyle{ \exists a \in A, P(a) }[/math]	[math]\displaystyle{ \Sigma a: A.P(a) }[/math]	Dependent Sum

Because the law of excluded middle does not hold, there is no term of type [math]\displaystyle{ \Pi a.A+ (A\to\bot) }[/math]. Likewise, double negation does not hold, so there is no term of type [math]\displaystyle{ \Pi A.((A\to\bot)\to\bot)\to A }[/math].

It is possible to include the law of excluded middle and double negation into a type theory, by rule or assumption. However, terms may not compute down to canonical terms and it will interfere with the ability to determine if two terms are judgementally equal to each other.

Constructive mathematics

Per Martin-Löf proposed his intuitionistic type theory as a foundation for constructive mathematics. Constructive mathematics requires when proving "there exists an [math]\displaystyle{ x }[/math] with property [math]\displaystyle{ P(x) }[/math]", one must construct a particular [math]\displaystyle{ x }[/math] and a proof that it has property [math]\displaystyle{ P }[/math]. In type theory, existence is accomplished using the dependent product type, and its proof requires a term of that type.

An example of a non-constructive proof is proof by contradiction. The first step is assuming that [math]\displaystyle{ x }[/math] does not exist and refuting it by contradiction. The conclusion from that step is "it is not the case that [math]\displaystyle{ x }[/math] does not exist". The last step is, by double negation, concluding that [math]\displaystyle{ x }[/math] exists. Constructive mathematics does not allow the last step of removing the double negation to conclude that [math]\displaystyle{ x }[/math] exists.

Most of the type theories proposed as foundations are constructive, and this includes most of the ones used by proof assistants. It is possible to add non-constructive features to a type theory, by rule or assumption. These include operators on continuations such as call with current continuation. However, these operators tend to break desirable properties such as canonicity and parametricity.

Curry-Howard correspondence

The Curry–Howard correspondence is the observed similarity between logics and programming languages. The implication in logic, "A [math]\displaystyle{ \to }[/math] B" resembles a function from type "A" to type "B". For a variety of logics, the rules are similar to expressions in a programming language's types. The similarity goes farther, as applications of the rules resemble programs in the programming languages. Thus, the correspondence is often summarized as "proofs as programs".

The opposition of terms and types can also be viewed as one of implementation and specification. By program synthesis, (the computational counterpart of) type inhabitation can be used to construct (all or parts of) programs from the specification given in the form of type information.

Type inference

Many programs that work with type theory (e.g., interactive theorem provers) also do type inferencing. It lets them select the rules that the user intends, with fewer actions by the user.

Research areas

Category theory

Although the initial motivation for category theory was far removed from foundationalism, the two fields turned out to have deep connections. As John Lane Bell writes: "In fact categories can themselves be viewed as type theories of a certain kind; this fact alone indicates that type theory is much more closely related to category theory than it is to set theory." In brief, a category can be viewed as a type theory by regarding its objects as types (or sorts), i.e. "Roughly speaking, a category may be thought of as a type theory shorn of its syntax." A number of significant results follow in this way:

• cartesian closed categories correspond to the typed λ-calculus (Lambek, 1970);
• C-monoids (categories with products and exponentials and one non-terminal object) correspond to the untyped λ-calculus (observed independently by Lambek and Dana Scott around 1980);
• locally cartesian closed categories correspond to Martin-Löf type theories (Seely, 1984).

The interplay, known as categorical logic, has been a subject of active research since then; see the monograph of Jacobs (1999) for instance.

Honmotopy type theory

Homotopy type theory attempts to combine type theory and category theory. It focuses on equalities, especially equalities between types.Homotopy type theory differs from intuitionistic type theory mostly by its handling of the equality type. In 2016 cubical type theory was proposed, which is a homotopy type theory with normalization.

Definitions

Terms and types

Atomic terms

The most basic types are called atoms, and a term whose type is an atom is known as an atomic term. Common atomic terms included in type theories are natural numbers, often notated with the type [math]\displaystyle{ \mathsf{nat} }[/math], Boolean logic values ([math]\displaystyle{ \mathrm{true} }[/math]/[math]\displaystyle{ \mathrm{false} }[/math]), notated with the type [math]\displaystyle{ \mathsf{bool} }[/math], and formal variables, whose type may vary. For example, the following may be atomic terms.

• [math]\displaystyle{ 42:\mathsf{nat} }[/math]
• [math]\displaystyle{ \mathrm{true}:\mathsf{bool} }[/math]
• [math]\displaystyle{ x:\mathsf{nat} }[/math]
• [math]\displaystyle{ y:\mathsf{bool} }[/math]

Function terms

In addition to atomic terms, most modern type theories also allow for functions. Function types introduce an arrow symbol, and are defined inductively: If [math]\displaystyle{ \sigma }[/math] and [math]\displaystyle{ \tau }[/math] are types, then the notation [math]\displaystyle{ \sigma\to\tau }[/math] is the type of a function which takes a parameter of type [math]\displaystyle{ \sigma }[/math] and returns a term of type [math]\displaystyle{ \tau }[/math]. Types of this form are known as simple types.

Some terms may be declared directly as having a simple type, such as the following term, [math]\displaystyle{ \mathrm{add} }[/math], which takes in two natural numbers in sequence and returns one natural number.

[math]\displaystyle{ \mathrm{add}:\mathsf{nat}\to (\mathsf{nat}\to\mathsf{nat}) }[/math]

Strictly speaking, a simple type only allows for one input and one output, so a more faithful reading of the above type is that [math]\displaystyle{ \mathrm{add} }[/math] is a function which takes in a natural number and returns a function of the form [math]\displaystyle{ \mathsf{nat}\to\mathsf{nat} }[/math]. The parentheses clarify that [math]\displaystyle{ \mathrm{add} }[/math] does not have the type [math]\displaystyle{ (\mathsf{nat}\to \mathsf{nat})\to\mathsf{nat} }[/math], which would be a function which takes in a function of natural numbers and returns a natural number. The convention is that the arrow is right associative, so the parentheses may be dropped from [math]\displaystyle{ \mathrm{add} }[/math]'s type.

Lambda terms

New function terms may be constructed using lambda expressions, and are called lambda terms. These terms are also defined inductively: a lambda term has the form [math]\displaystyle{ (\lambda v .t) }[/math], where [math]\displaystyle{ v }[/math] is a formal variable and [math]\displaystyle{ t }[/math] is a term, and its type is notated [math]\displaystyle{ \sigma\to\tau }[/math], where [math]\displaystyle{ \sigma }[/math] is the type of [math]\displaystyle{ v }[/math], and [math]\displaystyle{ \tau }[/math] is the type of [math]\displaystyle{ t }[/math]. The following lambda term represents a function which doubles an input natural number.

[math]\displaystyle{ (\lambda x.\mathrm{add}\,x\,x): \mathsf{nat}\to\mathsf{nat} }[/math]

The variable is [math]\displaystyle{ x }[/math] and (implicit from the lambda term's type) must have type [math]\displaystyle{ \mathsf{nat} }[/math]. The term [math]\displaystyle{ \mathrm{add}\,x\,x }[/math] has type [math]\displaystyle{ \mathsf{nat} }[/math], which is seen by applying the function application inference rule twice. Thus, the lambda term has type [math]\displaystyle{ \mathsf{nat}\to\mathsf{nat} }[/math], which means it is a function taking a natural number as an argument and returning a natural number.

A lambda term is often referred to as an anonymous function because it lacks a name. The concept of anonymous functions appears in many programming languages.

Inference Rules

Function application

The power of type theories is in specifying how terms may be combined by way of inference rules. Type theories which have functions also have the inference rule of function application: if [math]\displaystyle{ t }[/math] is a term of type [math]\displaystyle{ \sigma\to\tau }[/math], and [math]\displaystyle{ s }[/math] is a term of type [math]\displaystyle{ \sigma }[/math], then the application of [math]\displaystyle{ t }[/math] to [math]\displaystyle{ s }[/math], often written [math]\displaystyle{ (t\,s) }[/math], has type [math]\displaystyle{ \tau }[/math]. For example, if one knows the type notations [math]\displaystyle{ 0:\textsf{nat} }[/math], [math]\displaystyle{ 1:\textsf{nat} }[/math], and [math]\displaystyle{ 2:\textsf{nat} }[/math], then the following type notations can be deduced from function application.

• [math]\displaystyle{ (\mathrm{add}\,1): \textsf{nat}\to\textsf{nat} }[/math]
• [math]\displaystyle{ ((\mathrm{add}\,2)\,0): \textsf{nat} }[/math]
• [math]\displaystyle{ ((\mathrm{add}\,1)((\mathrm{add}\,2)\,0)): \textsf{nat} }[/math]

Parentheses indicate the order of operations; however, by convention, function application is left associative, so parentheses can be dropped where appropriate. In the case of the three examples above, all parentheses could be omitted from the first two, and the third may simplified to [math]\displaystyle{ \mathrm{add}\,1\, (\mathrm{add}\,2\,0): \textsf{nat} }[/math].

Reductions

Type theories that allow for lambda terms also include inference rules known as [math]\displaystyle{ \beta }[/math]-reduction and [math]\displaystyle{ \eta }[/math]-reduction. They generalize the notion of function application to lambda terms. Symbolically, they are written

• [math]\displaystyle{ (\lambda v. t)\,s\rightarrow t[v \colon= s] }[/math] ([math]\displaystyle{ \beta }[/math]-reduction).
• [math]\displaystyle{ (\lambda v. t\, v)\rightarrow t }[/math], if [math]\displaystyle{ v }[/math] is not a free variable in [math]\displaystyle{ t }[/math] ([math]\displaystyle{ \eta }[/math]-reduction).

The first reduction describes how to evaluate a lambda term: if a lambda expression [math]\displaystyle{ (\lambda v .t) }[/math] is applied to a term [math]\displaystyle{ s }[/math], one replaces every occurrence of [math]\displaystyle{ v }[/math] in [math]\displaystyle{ t }[/math] with [math]\displaystyle{ s }[/math]. The second reduction makes explicit the relationship between lambda expressions and function types: if [math]\displaystyle{ (\lambda v. t\, v) }[/math] is a lambda term, then it must be that [math]\displaystyle{ t }[/math] is a function term because it is being applied to [math]\displaystyle{ v }[/math]. Therefore, the lambda expression is equivalent to just [math]\displaystyle{ t }[/math], as both take in one argument and apply [math]\displaystyle{ t }[/math] to it.

For example, the following term may be [math]\displaystyle{ \beta }[/math]-reduced.

[math]\displaystyle{ (\lambda x.\mathrm{add}\,x\,x)\,2\rightarrow \mathrm{add}\,2\,2 }[/math]

In type theories that also establish notions of equality for types and terms, there are corresponding inference rules of [math]\displaystyle{ \beta }[/math]-equality and [math]\displaystyle{ \eta }[/math]-equality.

Common terms and types

Empty type

The empty type has no terms. The type is usually written [math]\displaystyle{ \bot }[/math] or [math]\displaystyle{ \mathbb 0 }[/math]. One use for the empty type is proofs of type inhabitation. If for a type [math]\displaystyle{ a }[/math], it is consistent to derive a function of type [math]\displaystyle{ a\to\bot }[/math], then [math]\displaystyle{ a }[/math] is uninhabited, which is to say it has no terms.

Unit type

The unit type has exactly 1 canonical term. The type is written [math]\displaystyle{ \top }[/math] or [math]\displaystyle{ \mathbb 1 }[/math] and the single canonical term is written [math]\displaystyle{ \ast }[/math]. The unit type is also used in proofs of type inhabitation. If for a type [math]\displaystyle{ a }[/math], it is consistent to derive a function of type [math]\displaystyle{ \top\to a }[/math], then [math]\displaystyle{ a }[/math] is inhabited, which is to say it must have one or more terms.

Boolean type

The Boolean type has exactly 2 canonical terms. The type is usually written [math]\displaystyle{ \textsf{bool} }[/math] or [math]\displaystyle{ \mathbb B }[/math] or [math]\displaystyle{ \mathbb 2 }[/math]. The canonical terms are usually [math]\displaystyle{ \mathrm{true} }[/math] and [math]\displaystyle{ \mathrm{false} }[/math].

Natural numbers

Natural numbers are usually implemented in the style of Peano Arithmetic. There is a canonical term [math]\displaystyle{ 0:\mathsf{nat} }[/math] for zero. Canonical values larger than zero use iterated applications of a successor function [math]\displaystyle{ \mathrm{S}:\mathsf{nat}\to\mathsf{nat} }[/math].

Dependent typing

Some type theories allow for types of complex terms, such as functions or lists, to depend on the types of its arguments. For example, a type theory could have the dependent type [math]\displaystyle{ \mathsf{list}\,a }[/math], which should correspond to lists of terms, where each term must have type [math]\displaystyle{ a }[/math]. In this case, [math]\displaystyle{ \mathsf{list} }[/math] has the type [math]\displaystyle{ U\to U }[/math], where [math]\displaystyle{ U }[/math] denotes the universe of all types in the theory.

Some theories also permit types to be dependent on terms instead of types. For example, a theory could have the type [math]\displaystyle{ \mathsf{vector}\,n }[/math], where [math]\displaystyle{ n }[/math] is a term of type [math]\displaystyle{ \mathsf{nat} }[/math] encoding the length of the vector. This allows for greater specificity and type safety: functions with vector length restrictions or length matching requirements, such as the dot product, can encode this requirement as part of the type.

There are foundational issues that can arise from dependent types if a theory is not careful about what dependencies are allowed, such as Girard's Paradox. The logician Henk Barendegt introduced the lambda cube as a framework for studying various restrictions and levels of dependent typing.

Product type

The product type depends on two types, and its terms are commonly written as ordered pairs [math]\displaystyle{ (s,t) }[/math] or with the symbol [math]\displaystyle{ \times }[/math]. The pair [math]\displaystyle{ (s,t) }[/math] has the product type [math]\displaystyle{ \sigma\times\tau }[/math], where [math]\displaystyle{ \sigma }[/math] is the type of [math]\displaystyle{ s }[/math] and [math]\displaystyle{ \tau }[/math] is the type of [math]\displaystyle{ t }[/math]. The product type is usually defined with eliminator functions [math]\displaystyle{ \mathrm{first}:(\Pi\,\sigma\,\tau.\sigma\times\tau\to\sigma) }[/math] and [math]\displaystyle{ \mathrm{second}:(\Pi\,\sigma\,\tau.\sigma\times\tau\to\tau) }[/math].

• [math]\displaystyle{ \mathrm{first}\,(s,t) }[/math] returns [math]\displaystyle{ s }[/math], and
• [math]\displaystyle{ \mathrm{second}\,(s,t) }[/math] returns [math]\displaystyle{ t }[/math].

Besides ordered pairs, this type is used for the concepts of logical conjunction and intersection.

Sum type

The sum type depends on two types, and it is commonly written with the symbol [math]\displaystyle{ + }[/math] or [math]\displaystyle{ \sqcup }[/math]. In programming languages, sum types may be referred to as tagged unions. The type [math]\displaystyle{ \sigma\sqcup\tau }[/math] is usually defined with constructors [math]\displaystyle{ \mathrm{left}:\sigma\to(\sigma\sqcup\tau) }[/math] and [math]\displaystyle{ \mathrm{right}:\tau\to(\sigma\sqcup\tau) }[/math], which are injective, and an eliminator function [math]\displaystyle{ \mathrm{match}:(\Pi\,\rho.(\sigma\to\rho)\to(\tau\to\rho)\to(\sigma\sqcup\tau)\to\rho) }[/math] such that

• [math]\displaystyle{ \mathrm{match}\,f\,g\,(\mathrm{left}\,x) }[/math] returns [math]\displaystyle{ f\,x }[/math], and
• [math]\displaystyle{ \mathrm{match}\,f\,g\,(\mathrm{right}\,y) }[/math] returns [math]\displaystyle{ g\,y }[/math].

The sum type is used for the concepts of logical disjunction and union.

Dependent products and sums

Two common type dependencies, dependent product and dependent sum types, allow for the theory to encode BHK intuitionistic logic by acting as equivalents to universal and existential quantification; this is formalized by Curry–Howard Correspondence. As they also connect to products and sums in set theory, they are often written with the symbols [math]\displaystyle{ \Pi }[/math] and [math]\displaystyle{ \Sigma }[/math], respectively. Dependent product and sum types commonly appear in function types and are frequently incorporated in programming languages.

For example, consider a function [math]\displaystyle{ \mathrm{append} }[/math], which takes in a [math]\displaystyle{ \mathsf{list}\,a }[/math] and a term of type [math]\displaystyle{ a }[/math], and returns the list with the element at the end. The type annotation of such a function would be [math]\displaystyle{ \mathrm{append}:(\Pi\,a.\mathsf{list}\,a\to a\to\mathsf{list}\,a) }[/math], which can be read as "for any type [math]\displaystyle{ a }[/math], pass in a [math]\displaystyle{ \mathsf{list}\,a }[/math] and an [math]\displaystyle{ a }[/math], and return a [math]\displaystyle{ \mathsf{list}\,a }[/math]".

Sum types are seen in dependent pairs, where the second type depends on the value of the first term. This arises naturally in computer science where functions may return different types of outputs based on the input. For example, the Boolean type is usually defined with an eliminator function [math]\displaystyle{ \mathrm{if} }[/math], which takes three arguments and behaves as follows.

• [math]\displaystyle{ \mathrm{if}\,\mathrm{true}\,x\,y }[/math] returns [math]\displaystyle{ x }[/math], and
• [math]\displaystyle{ \mathrm{if}\,\mathrm{false}\,x\,y }[/math] returns [math]\displaystyle{ y }[/math].

The return type of this function depends on its [math]\displaystyle{ \mathsf{bool} }[/math] input. If the type theory allows for dependent types, then it is possible to define a function [math]\displaystyle{ \mathrm{TF}\colon\mathsf{bool}\to U\to U\to U }[/math] such that

• [math]\displaystyle{ \mathrm{TF}\,\mathrm{true}\,\sigma\,\tau }[/math] returns [math]\displaystyle{ \sigma }[/math], and
• [math]\displaystyle{ \mathrm{TF}\,\mathrm{false}\,\sigma\,\tau }[/math] returns [math]\displaystyle{ \tau }[/math].

The type of [math]\displaystyle{ \mathrm{if} }[/math] may then be written as [math]\displaystyle{ (\Pi\,\sigma\,\tau.\mathsf{bool}\to\sigma\to\tau\to(\Sigma\,x:\textsf{bool}.\mathrm{TF}\,x\,\sigma\,\tau)) }[/math].

Identity type

Following the notion of Curry-Howard Correspondence, the identity type is a type introduced to mirror propositional equivalence, as opposed to the judgmental (syntactic) equivalence that type theory already provides.

An identity type requires two terms of the same type and is written with the symbol [math]\displaystyle{ = }[/math]. For example, if [math]\displaystyle{ x+1 }[/math] and [math]\displaystyle{ 1+x }[/math] are terms, then [math]\displaystyle{ x+1=1+x }[/math] is a possible type. Canonical terms are created with a reflexivity function, [math]\displaystyle{ \mathrm{refl} }[/math]. For a term [math]\displaystyle{ t }[/math], the call [math]\displaystyle{ \mathrm{refl}\,t }[/math] returns the canonical term inhabiting the type [math]\displaystyle{ t=t }[/math].

The complexities of equality in type theory make it an active research topic; homotopy type theory is a notable area of research that mainly deals with equality in type theory.

Inductive types

Inductive types are a general template for creating a large variety of types. In fact, all the types described above and more can be defined using the rules of inductive types. Two methods of generating inductive types are induction-recursion and induction-induction. A method that only uses lambda terms is Scott encoding.

Some proof assistants, such as Coq and Lean, are based on the calculus for inductive constructions, which is a calculus of constructions with inductive types.

Differences from set theory

The most commonly accepted foundation for mathematics is first-order logic with the language and axioms of Zermelo–Fraenkel set theory with the axiom of choice, abbreviated ZFC. Type theories having sufficient expressibility may also act as a foundation of mathematics. There are a number of differences between these two approaches.

• Set theory has both rules and axioms, while type theories only have rules. Type theories, in general, do not have axioms and are defined by their rules of inference.
• Classical set theory and logic have the law of excluded middle. When a type theory encodes the concepts of "and" and "or" as types, it leads to intuitionistic logic, and does not necessarily have the law of excluded middle.
• In set theory, an element is not restricted to one set. The element can appear in subsets and unions with other sets. In type theory, terms (generally) belong to only one type. Where a subset would be used, type theory can use a predicate function or use a dependently-typed product type, where each element [math]\displaystyle{ x }[/math] is paired with a proof that the subset's property holds for [math]\displaystyle{ x }[/math]. Where a union would be used, type theory uses the sum type, which contains new canonical terms.
• Type theory has a built-in notion of computation. Thus, "1+1" and "2" are different terms in type theory, but they compute to the same value. Moreover, functions are defined computationally as lambda terms. In set theory, "1+1=2" means that "1+1" is just another way to refer the value "2". Type theory's computation does require a complicated concept of equality.
• Set theory encodes numbers as sets. Type theory can encode numbers as functions using Church encoding, or more naturally as inductive types, and the construction closely resembles Peano's axioms.
• In type theory, proofs are types whereas in set theory, proofs are part of the underlying first-order logic.

Proponents of type theory will also point out its connection to constructive mathematics through the BHK interpretation, its connection to logic by the Curry–Howard isomorphism, and its connections to Category theory.

Properties of type theories

Terms usually belong to a single type. However, there are set theories that define "subtyping".

Computation takes place by repeated application of rules. Many types of theories are strongly normalizing, which means that any order of applying the rules will always end in the same result. However, some are not. In a normalizing type theory, the one-directional computation rules are called "reduction rules", and applying the rules "reduces" the term. If a rule is not one-directional, it is called a "conversion rule".

Some combinations of types are equivalent to other combinations of types. When functions are considered "exponentiation", the combinations of types can be written similarly to algebraic identities. Thus, [math]\displaystyle{ {\mathbb 0} + A \cong A }[/math], [math]\displaystyle{ {\mathbb 1} \times A \cong A }[/math], [math]\displaystyle{ {\mathbb 1} + {\mathbb 1} \cong {\mathbb 2} }[/math], [math]\displaystyle{ A^{B+C} \cong A^B \times A^C }[/math], [math]\displaystyle{ A^{B\times C} \cong (A^B)^C }[/math].

Axioms

Most type theories do not have axioms. This is because a type theory is defined by its rules of inference. This is a source of confusion for people familiar with Set Theory, where a theory is defined by both the rules of inference for a logic (such as first-order logic) and axioms about sets.

Sometimes, a type theory will add a few axioms. An axiom is a judgment that is accepted without a derivation using the rules of inference. They are often added to ensure properties that cannot be added cleanly through the rules.

Axioms can cause problems if they introduce terms without a way to compute on those terms. That is, axioms can interfere with the normalizing property of the type theory.

Some commonly encountered axioms are:

• "Axiom K" ensures "uniqueness of identity proofs". That is, that every term of an identity type is equal to reflexivity.
• "Univalence Axiom" holds that equivalence of types is equality of types. The research into this property led to cubical type theory, where the property holds without needing an axiom.
• "Law of Excluded Middle" is often added to satisfy users who want classical logic, instead of intuitionistic logic.

The Axiom of Choice does not need to be added to type theory, because in most type theories it can be derived from the rules of inference. This is because of the constructive nature of type theory, where proving that a value exists requires a method to compute the value. The Axiom of Choice is less powerful in type theory than most set theories, because type theory's functions must be computable and, being syntax-driven, the number of terms in a type must be countable. (See Axiom of choice § In constructive mathematics.)

List of type theories

Major

• Simply typed lambda calculus which is a higher-order logic
• intuitionistic type theory
• system F
• LF is often used to define other type theories
• calculus of constructions and its derivatives

Minor

• Automath
• ST type theory
• UTT (Luo's Unified Theory of dependent Types)
• some forms of combinatory logic
• others defined in the lambda cube (also known as pure type systems)
• others under the name typed lambda calculus

Active research

• Homotopy type theory explores equality of types
• Cubical Type Theory is an implementation of homotopy type theory

See also

• Foundations of mathematics
• Logic

Further reading

• Aarts, C.; Backhouse, R.; Hoogendijk, P.; Voermans, E.; van der Woude, J. (December 1992). "A Relational Theory of Datatypes". Technische Universiteit Eindhoven. https://www.researchgate.net/publication/277287583. 
• Andrews B., Peter (2002). An Introduction to Mathematical Logic and Type Theory: To Truth Through Proof (2nd ed.). Kluwer. ISBN 978-1-4020-0763-7. 
• Jacobs, Bart (1999). Categorical Logic and Type Theory. Studies in Logic and the Foundations of Mathematics. 141. Elsevier. ISBN 978-0-444-50170-7. https://www.cs.ru.nl/B.Jacobs/CLT/bookinfo.html. Retrieved 2020-07-19.  Covers type theory in depth, including polymorphic and dependent type extensions. Gives categorical semantics.
• Cardelli, Luca (1996). "Type Systems". in Tucker, Allen B.. The Computer Science and Engineering Handbook. CRC Press. pp. 2208–36. ISBN 9780849329098. http://citeseer.ist.psu.edu/cardelli97type.html. Retrieved 2004-06-26. 
• Collins, Jordan E. (2012). A History of the Theory of Types: Developments After the Second Edition of 'Principia Mathematica'. Lambert Academic Publishing. ISBN 978-3-8473-2963-3.  Provides a historical survey of the developments of the theory of types with a focus on the decline of the theory as a foundation of mathematics over the four decades following the publication of the second edition of 'Principia Mathematica'.
• Constable, Robert L. (2012). "Naïve Computational Type Theory". in Schwichtenberg, H.. Proof and System-Reliability. Nato Science Series II. 62. Springer. pp. 213–259. ISBN 9789401004138. http://www.nuprl.org/documents/Constable/naive.pdf.  Intended as a type theory counterpart of Paul Halmos's (1960) Naïve Set Theory
• Coquand, Thierry (2018). "Type Theory". Stanford Encyclopedia of Philosophy. http://plato.stanford.edu/entries/type-theory/. 
• Thompson, Simon (1991). Type Theory and Functional Programming. Addison–Wesley. ISBN 0-201-41667-0. http://www.cs.kent.ac.uk/people/staff/sjt/TTFP/. Retrieved 2006-04-03. 
• Hindley, J. Roger (2008). Basic Simple Type Theory. Cambridge University Press. ISBN 978-0-521-05422-5.  A good introduction to simple type theory for computer scientists; the system described is not exactly Church's STT though. Book review
• Kamareddine, Fairouz D.; Laan, Twan; Nederpelt, Rob P. (2004). A modern perspective on type theory: from its origins until today. Springer. ISBN 1-4020-2334-0. 
• Ferreirós, José; Domínguez, José Ferreirós (2007). "X. Logic and Type Theory in the Interwar Period". Labyrinth of thought: a history of set theory and its role in modern mathematics (2nd ed.). Springer. ISBN 978-3-7643-8349-7. 
• Laan, T.D.L. (1997). The evolution of type theory in logic and mathematics (PDF) (PhD). Eindhoven University of Technology. doi:10.6100/IR498552. ISBN 90-386-0531-5. Archived (PDF) from the original on 2022-10-09.
• Montague, R. (1973) "The proper treatment of quantification in ordinary English". In K. J. J. Hintikka, J. M. E. Moravcsik, and P. Suppes (eds.), Approaches to Natural Language (Synthese Library, 49), Dordrecht: Reidel, 221–242; reprinted in Portner and Partee (eds.) 2002, pp. 17–35. See: Montague Semantics, Stanford Encyclopedia of Philosophy.

External links

Introductory material

• Type Theory at nLab, which has articles on many topics.
• Intuitionistic Type Theory article at the Stanford Encyclopedia of Philosophy
• Lambda Calculi with Types book by Henk Barendregt
• Calculus of Constructions / Typed Lambda Calculus textbook style paper by Helmut Brandl
• Intuitionistic Type Theory notes by Per Martin-Löf
• Programming in Martin-Löf's Type Theory book
• Homotopy Type Theory book, which proposed homotopy type theory as a mathematical foundation.

Advanced material

• The TYPES Forum — moderated e-mail forum focusing on type theory in computer science, operating since 1987.
• The Nuprl Book: "Introduction to Type Theory."
• Types Project lecture notes of summer schools 2005–2008
  • The 2005 summer school has introductory lectures
• Oregon Programming Languages Summer School, many lectures and some notes.
  • Summer 2013 lectures including Robert Harper's talks on YouTube
  • Summer 2015 Types, Logic, Semantics, and Verification
• Andrej Bauer's blog